Subscription fall-back in a radio communication network

ABSTRACT

A method is described herein that is performed by a connectivity service platform in a communication network. The platform is enabled to communicate with a radio device via a wireless network connection of a first subscription of the radio device. The method comprises falling back to a second subscription, thereby enabling the connectivity service platform to communicate with the radio device via a wireless network connection of said second subscription of the radio device instead of the first subscription. The method also comprises receiving a request message from the radio device via the network connection of the first subscription. The method also comprises sending a reject message to the radio device, in response to the received request message and in view of the platform having fallen back to the second subscription. The reject message comprises a fall-back indication for instructing the radio device to fall back from the first subscription.

CLAIM OF PRIORITY

This application is a continuation application of U.S. patentapplication Ser. No. 15/303,186, filed Oct. 10, 2016, now pending, whichis a 371 of International Application No. PCT/SE2014/050445, filed Apr.10, 2014. The contents of these documents are hereby incorporated byreference herein.

TECHNICAL FIELD

The present disclosure relates to methods and devices of a communicationnetwork for managing subscriptions for wireless connection of a radiodevice, e.g. a radio device having an embedded Universal IntegratedCircuit Card (eUICC).

BACKGROUND

Unlike a traditional UICC Subscriber Identity Module (SIM) card used ina consumer device, e.g. a mobilie phone, all eUICC that are deployed ine.g. Machine-to-Machine (M2M) solutions and embedded into the M2M devicecannot easily be accessed by human intervention to switch the SIM cardmanually during the device life cycle. According to the Global Systemfor Mobile Communications (GSM) Association (GSMA) eUICC standard (GSMA“Remote Provisioning Architecture for Embedded UICC” DRAFT 1.39 29thApril 2013) and European Telecommunications Standards Institute (ETSI)eUICC Standard (EXALTED “Expanding LTE for Devices” FP7 Contract Number:258512, Feb. 29, 2012), all eUICC shall be delivered with apre-installed provisioning subscription for remoteprovisioning/bootstrapping purpose (i.e. a provisioning/bootstrappingoperator provides initial bootstrapping connectivity for eUICC in orderto enable late binding feature i.e. to remotely provision the 1^(st)eUICC operational subscription to the eUICC when the device (e.g. a car)comprising the eUICC is shipped from initial manufacturer country to thedestination country (1^(st) operational subscription could be providedby the local operator from the destination country), and then later tochange the eUICC active operational subscription from the currentoperator subscription to an new operator (due to the location beingchanged to another country, or changed operator subscription) during thedevice/eUICC long life cycle (15-20 years), in order to avoid highroaming fee and/or single operator lock-in situation during the devicelong life cycle e.g. in the automotive industry or for smartmetering/security cameras etc.

However, eUICC connectivity may be lost permanently during subscriptionmanagement lifecycle through operations such asenable/disable/activate/pause/deactivate/terminate/etc. In such casesthe eUICC and network must fall back to an available subscription torecover the initial connectivity.

Chapter 3.5.12 “Fall-Back Mechanism” of GSMA “Remote ProvisioningArchitecture for Embedded UICC” DRAFT 1.39 29 Apr. 2013 states that inthe event of loss of network connectivity, as detected by the device,there is a need to change to the profile with fall-back attribute set.In this case the eUICC disables the currently enabled Profile (ProfileA) and enables the Profile with Fall-back Attribute set (Profile B). Thedevice reports network loss to the eUICC. The eUICC is configured toperform the fall-back mechanism if certain network connectivity issuesare reported by the Device.

SUMMARY

It has been realised that it may be difficult to fall back since theradio device may have lost network connectivity and may not have anactive secondary subscription to fall back to. It can thus not contact awireless network of another operator to set up another subscriptionsince it does not have network connectivity.

Subscriptions of radio devices, e.g. M2M devices, may be handled via aconnectivity service platform, e.g. the Ericsson Device ConnectionPlatform (DCP) or other hosted core network (CN) or home public landmobile network (Home PLMN or HPLMN) which may be used by severaldifferent network operators to manage subscriptions for radio deviceshaving eUICC (since the subscriptions are not handled manually byinserting a UICC card in the device). Thus, a host may host amulti-tenant home location register (HLR) and other core network nodes(Gateway General Packet Radio Service (GPRS) support node (GGSN), shortmessage service centre (SMSC), etc.) in HPLMN as a core network servicefor e.g. all customer operators. All the M2M subscribers of theoperators may be registered and stored on hosted HLR. Connectivity isprovided as a service to all operators hosted on the platform. On top ofthe core network service, also a business support system (BSS), e.g. acloud BSS, may be hosted to provision and manage subscriber data,processes, billing, etc. In accordance with the present disclosure,features for supporting i.a. eUICC are added in the connectivity serviceplatform to meet the new developments within this field (eUICC for M2Mconnections from vehicles (cars), smart metering, security camera, andalso for consumer electronics etc.).

According to an aspect of the present disclosure, there is provided amethod performed by a connectivity service platform in a communicationnetwork. The platform is enabled to communicate with a radio device viaa wireless network connection of a first subscription of the radiodevice. The method comprises falling back to a second subscription,thereby enabling the connectivity service platform to communicate withthe radio device via a wireless network connection of said secondsubscription of the radio device instead of the first subscription. Themethod also comprises receiving a request message from the radio devicevia the network connection of the first subscription. The method alsocomprises sending a reject message to the radio device, in response tothe received request message and in view of the platform having fallenback to the second subscription. The reject message comprises afall-back indication for instructing the radio device to fall back fromthe first subscription.

According to another aspect of the present disclosure, there is provideda connectivity service platform for a communication network. Theplatform comprises processor circuitry, and storage storing instructionsexecutable by said processor circuitry whereby said connectivity serviceplatform is operative to be enabled to communicate with a radio devicevia a wireless network connection of a first subscription of the radiodevice. The platform is also operative to fall back to a secondsubscription, thereby enabling the connectivity service platform tocommunicate with the radio device via a wireless network connection ofsaid second subscription of the radio device instead of the firstsubscription. The platform is also operative to receive a requestmessage from the radio device via the network connection of the firstsubscription. The platform is also operative to send a reject message tothe radio device, in response to the received request message and inview of the platform having fallen back to the second subscription. Thereject message comprises a fall-back indication for instructing theradio device to fall back from the first subscription.

According to another aspect of the present disclosure, there is provideda method performed by a radio device in a communication network. Themethod comprises sending a request message uplink via a wireless networkconnection of a first subscription of the radio device. The method alsocomprises receiving a reject message from a connectivity serviceplatform, in response to the sent request message. The reject messagecomprises a fall-back indication instructing the radio device to fallback from the first subscription. The method also comprises falling backin accordance with the received fall-back indication, to a secondsubscription of the radio device, thereby enabling the radio device toobtain a wireless network connection of the second subscription insteadof the first subscription.

According to another aspect of the present disclosure, there is provideda radio device for a communication network. The radio device comprisesprocessor circuitry, and storage storing instructions executable by saidprocessor circuitry whereby said radio device is operative to send arequest message uplink via a wireless network connection of a firstsubscription of the radio device. The radio device is also operative toreceive a reject message from a connectivity service platform, inresponse to the sent request message. The reject message comprises afall-back indication instructing the radio device to fall back from thefirst subscription. The radio device is also operative to fall back inaccordance with the received fall-back indication, to a secondsubscription of the radio device, thereby enabling the radio device toobtain a wireless network connection of the second subscription insteadof the first subscription.

According to another aspect of the present disclosure, there is provideda computer program product comprising computer-executable components forcausing a connectivity service platform to perform an embodiment of amethod of the present disclosure when the computer-executable componentsare run on processor circuitry comprised in the connectivity serviceplatform.

According to another aspect of the present disclosure, there is provideda computer program product comprising computer-executable components forcausing a radio device to perform an embodiment of a method of thepresent disclosure when the computer-executable components are run onprocessor circuitry comprised in the radio device.

According to another aspect of the present disclosure, there is provideda computer program comprising computer program code which is able to,when run on processor circuitry of a connectivity service platform,cause the connectivity service platform to be enabled to communicatewith a radio device via a wireless network connection of a firstsubscription of the radio device. The code is also able to cause theconnectivity service platform to fall back to a second subscription,thereby enabling the connectivity service platform to communicate withthe radio device via a wireless network connection of said secondsubscription of the radio device instead of the first subscription. Thecode is also able to cause the connectivity service platform to receivea request message from the radio device via the network connection ofthe first subscription. The code is also able to cause the connectivityservice platform to send a reject message to the radio device, inresponse to the received request message and in view of the platformhaving fallen back to the second subscription. The reject messagecomprising a fall-back indication for instructing the radio device tofall back from the first subscription.

According to another aspect of the present disclosure, there is provideda computer program comprising computer program code which is able to,when run on processor circuitry of a radio device in a communicationnetwork, cause the radio device to send a request message uplink via awireless network connection of a first subscription of the radio device.The code is also able to cause the radio device to receive a rejectmessage from a connectivity service platform, in response to the sentrequest message. The reject message comprises a fall-back indicationinstructing the radio device to fall back from the first subscription.The code is also able to cause the radio device to fall back inaccordance with the received fall-back indication, to a secondsubscription of the radio device, thereby enabling the radio device toobtain a wireless network connection of the second subscription insteadof the first subscription.

According to another aspect of the present disclosure, there is provideda computer program product comprising an embodiment of a computerprogram of the present disclosure and a computer readable means on whichthe computer program is stored.

By the connectivity service platform (below also called “the platform”)including the fall-back indication in its reject message to the radiodevice, the radio device is informed that it should fall-back to itssecond subscription in order to regain network connectivity. Thefall-back indication may e.g. comprise information about whichsubscription the radio device should fall back to in order to mirror thefalling back already done by the platform, or comprise an indication forthe radio device to follow its already stored fall-back policy whichtypically corresponds (or is the same as) the fall-back policy of theplatform whereby the radio device can mirror the falling back of theplatform to the second subscription. The platform may e.g. when it fallsback, store an instruction to include the fall-back indication with areject message if the radio device attempts to connect via the firstsubscription. It is also noted that there may be no need for having asynchronization mechanism between the platform and the device/UICC forsynchronizing the subscription used.

Generally, all terms used in the claims are to be interpreted accordingto their ordinary meaning in the technical field, unless explicitlydefined otherwise herein. All references to “a/an/the element,apparatus, component, means, step, etc.” are to be interpreted openly asreferring to at least one instance of the element, apparatus, component,means, step, etc., unless explicitly stated otherwise. The steps of anymethod disclosed herein do not have to be performed in the exact orderdisclosed, unless explicitly stated. The use of “first”, “second” etc.for different features/components of the present disclosure are onlyintended to distinguish the features/components from other similarfeatures/components and not to impart any order or hierarchy to thefeatures/components.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be described, by way of example, with reference to theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating an embodiment of acommunication network in accordance with the present disclosure.

FIG. 2 is a schematic block diagram of an embodiment of a connectivityservice platform of the present disclosure.

FIG. 3 is a schematic block diagram of an embodiment of a radio deviceof the present disclosure.

FIG. 4 is a schematic illustration of an embodiment of a computerprogram product of the present disclosure.

FIG. 5a is a schematic flow chart of an embodiment of a method of aconnectivity service platform, of the present disclosure.

FIG. 5b is a schematic flow chart of another embodiment of a method of aconnectivity service platform, of the present disclosure.

FIG. 6a is a schematic flow chart of an embodiment of a method of aradio device, of the present disclosure.

FIG. 6b is a schematic flow chart of another embodiment of a method of aradio device, of the present disclosure.

FIG. 7 is a schematic signalling diagram illustrating embodiments of thepresent disclosure.

FIG. 8 is a schematic block diagram illustrating example embodiments ofthe present disclosure.

DETAILED DESCRIPTION

Embodiments will now be described more fully hereinafter with referenceto the accompanying drawings, in which certain embodiments are shown.However, other embodiments in many different forms are possible withinthe scope of the present disclosure. Rather, the following embodimentsare provided by way of example so that this disclosure will be thoroughand complete, and will fully convey the scope of the disclosure to thoseskilled in the art. Like numbers refer to like elements throughout thedescription.

FIG. 1 is a schematic block diagram illustrating an embodiment of acommunication network 1 in accordance with the present disclosure. Thecommunication network 1 comprises a connectivity service platform 2,e.g. an Ericsson Device Connection Platform (EDCP or DCP) for providingCN functionality for customers in the form of several different mobilenetwork operators (MNO:s) for a plurality of radio devices 5 havingeUICC 6, e.g. M2M devices 5. Each of the radio devices 5 may be anydevice or user equipment (UE), mobile or stationary, enabled tocommunicate over a radio cannel in a communications network, forinstance but not limited to e.g. mobile phone, smart phone, modem,sensors, meters, vehicles such as cars or the like, householdappliances, medical appliances, media players, cameras, or any type ofconsumer electronic, for instance but not limited to television, radio,lighting arrangements, tablet computer, laptop, or personal computer(PC). The connectivity service platform 2 of the embodiment of FIG. 1comprises a cloud business support system (BSS) 3 as well as a cloudhome public land mobile network (HPLMN) 4. The HPLMN 4 comprises anyregular CN nodes or modules of a radio communication network, e.g. homelocation register (HLR), Gateway General Packet Radio Service (GPRS)support node (GGSN), short message service centre (SMSC), SignalTransfer Point (STP), Domain Name System (DNS), and authentication,authorization and accounting (AAA) RADIUS, for e.g. Signalling System 7(SS7) and/or Integrated Services Digital Network (ISDN) communicationsprotocols of signalling transport (SIGTRAN). The radio device 5 has awireless connection to the network 1 and the platform 2 via a wirelessconnection provided by a visited PLMN (VPLMN) of a network operator 7 or8. Each of the VPLMN also comprise the nodes and modules typical forsuch networks, e.g. a serving general packet radio service, GPRS,support node (SGSN), a mobile switching centre (MSC), a Domain NameSystem (DNS) server, a Signal Transfer Point (STP), a firewall etc. Eachoperator 7, 8 has a radio access network (RAN) with base stations viawhich radio devices may connect wirelessly provided that they have anenabled and active subscription with the operator. Since the radiodevice has an eUICC, the eUICC needs to be flash updated in order tochange to a new subscription for its wireless connection. Instructionsfor the update need typically be received via its wireless connection ofan old subscription before the change to the new subscription. The newsubscription, may be with the same operator 7 as the old subscription,but it may more commonly be with a new operator 8. It should be notedthat embodiments of the present disclosure may also be relevant forradio devices which do not have an eUICC, e.g. having a regular(removable) UICC or SIM card.

Embodiments of the present disclosure may be convenient e.g. in caseswhere the network side, i.e. the platform 2 has implemented a fall-backmechanism or otherwise has changed its subscription for the radio device5 but where the radio device 5 still uses the old subscription, i.e. hasnot fallen back to the subscription which is active in the platform 2.

In an example, the network side (platform 2) has performed fall-backfrom the current MNO 7 IMSI to the MNO 8 provisioning IMSI, and shallstore a fall-back message which indicates that the specific eUICC(ID) ofthe radio device 5 has changed active subscription from MNO 7 IMSI tothe MNO 8 provisioning IMSI, and then when the network side receives ae.g. attach request message (with the current MNO 7 IMSI) from the radiodevice 5, e.g. from the eUICC 6, it shall notify the device/eUICC thefall-back message/indication through the attach reject message. Theradio device 5 receives the attach reject message and analyses thefall-back indication, and shall then execute the subscription changefrom current MNO 7 IMSI to the MNO 8 provisioning (fall-back) IMSI, sothat the device 5/eUICC 6 can use the provisioning (fall-back) IMSI toreattach to the network/platform 2. Thereby the fall-back can be donesuccessfully for both device/eUICC and the network/platform. Here it isassumed that the provisioning subscription is the fall-back subscriptionused for fall-back purpose. However, if there are other availablesubscriptions (operational subscription) existing on both device/eUICCand network/platform (DCP) that has a fall-back attribute enabled, it isalternatively possible to fall-back to that subscription.

FIG. 2 is a schematic block diagram of an embodiment of a connectivityservice platform 2 of the present disclosure. The platform 2 comprisesprocessor circuitry 21 e.g. a central processing unit (CPU). Theprocessor circuitry 21 may comprise one or a plurality of processingunits in the form of microprocessor(s). However, other suitable deviceswith computing capabilities could be comprised in the processor 21, e.g.an application specific integrated circuit (ASIC), a field programmablegate array (FPGA) or a complex programmable logic device (CPLD). Theprocessor circuitry 21 is configured to run one or several computerprogram(s) or software (SW) 41 stored in a storage 26 e.g. comprising amemory. The processor circuitry comprises one or several modules 22, 24and 25 as a result of executing SW 41 in the storage 26, e.g. thefall-back detector 22, a subscription change component (SCC) 24 and/or asubscription fall-back component (SFC) 25 which is below, in FIG. 8, asan example depicted as comprising the fall-back event detector 22 aswell as the executed fall-back policy 27. Each of these modules may beformed by separate or dedicated processors of the processor circuitry 21or by a common processor. The storage 26 may comprise one or severalstorage units, of one or several type(s), each of which can be regardedas a computer readable means as discussed herein and may e.g. be in theform of a Random Access Memory (RAM), a Flash memory or other solidstate memory, or a hard disk, or be a combination thereof. Also the HLR28 as well as the fall-back policy 27 is part of/stored in the storage26. The processor circuitry 21 is also configured to store data in thestorage 26, as needed. The platform 2 also comprises a communicationinterface 29 for communication with the radio device 5 as well as withother parts of the communication network 1 such as the operators 7 and8. The communication interface may comprise a transmitter and a receiverfor, in cooperation with the processor circuitry 21, sending andreceiving data messages and other digital signalling.

FIG. 3 is a schematic block diagram of an embodiment of a radio device 5of the present disclosure. The radio device 5 comprises processorcircuitry 31 e.g. a central processing unit (CPU). The processorcircuitry 31 may comprise one or a plurality of processing units in theform of microprocessor(s). However, other suitable devices withcomputing capabilities could be comprised in the processor circuitry 31,e.g. an application specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or a complex programmable logic device(CPLD). The processor circuitry 31 is configured to run one or severalcomputer program(s) or software (SW) 41 stored in a storage 36 e.g.comprising a memory. The processor circuitry comprises one or severalmodules 32, 34 and 35 as a result of executing SW 41 in the storage 36,e.g. the fall-back detector 32, a subscription change component (SCC) 34and/or a subscription fall-back component (SFC) 35 which is below, inFIG. 8, as an example depicted as comprising the fall-back eventdetector 32 as well as the executed fall-back policy 37. Each of thesemodules may be formed by separate or dedicated processors of theprocessor circuitry 31 or by a common processor. The storage 36 maycomprise one or several storage units, of one or several type(s), eachof which can be regarded as a computer readable means as discussedherein and may e.g. be in the form of a Random Access Memory (RAM), aFlash memory or other solid state memory, or a hard disk, or be acombination thereof. Also the eUICC 6 of the device 5 as well as thefall-back policy 37 is part of/stored in the storage 36. The processorcircuitry 31 is also configured to store data in the storage 36, asneeded. The radio device 5 also comprises a radio communicationinterface 39 for communication with the platform 2 as well as with otherparts of the communication network 1 such as the operators 7 and 8. Thecommunication interface may comprise a transmitter and a receiver, aswell as an antenna, for, in cooperation with the processor circuitry 31,sending and receiving data messages and other digital signallingwirelessly.

FIG. 4 illustrates a computer program product 40. The computer programproduct 40 comprises a computer readable medium 42 comprising a computerprogram 41 in the form of computer-executable components 41. Thecomputer program/computer-executable components 41 may be configured tocause the platform 2 or the radio device 5 as discussed herein toperform an embodiment of a method of the present disclosure. Thecomputer program/computer-executable components may be run on theprocessor circuitry 21 of the platform 2 or the processor circuitry 31of the radio device 5 for causing the platform/radio device to performthe method. The computer program product 40 may e.g. be comprised in astorage 26 or 36 comprised in the platform/radio device and associatedwith the processor circuitry 21 or 31. Alternatively, the computerprogram product 40 may be, or be part of, a separate, e.g. mobile,storage means, such as a computer readable disc, e.g. CD or DVD or harddisc/drive, or a solid state storage medium, e.g. a RAM or Flash memory.

FIG. 5a is a flow chart illustrating an embodiment of a method of thepresent disclosure. The method is performed by a connectivity serviceplatform 2 in a communication network 1. The platform 2 is enabled tocommunicate with a radio device 5 via a wireless network connection of afirst subscription of the radio device. Then, for some reason, theplatform 2 decides to fall back 52 to a second subscription, therebyenabling the connectivity service platform 2 to communicate with theradio device 5 via a wireless network connection of said secondsubscription of the radio device instead of the first subscription. Forinstance, the fall-back may triggered by a fall-back function in the BSS3, and the BSS may notify the HLR 28 to fall-back to the secondsubscription, so both BSS 3 and HLR 28 will activate the secondsubscription, which means the device 5 (with the relevant eUICC ID) willbe allowed network access via the second subscription. However, theradio device 5 may not yet be enabled to communicate by means of itssecond subscription. Rather, the platform 2 receives 53 a requestmessage from the radio device 5 via the network connection of the firstsubscription, i.e. the subscription which is no longer active in theplatform 2. In response to the received 53 request message, the platform2 sends 54 a reject message to the radio device 5. In view of theplatform 2 having fallen back 52 to the second subscription, the rejectmessage comprises a fall-back indication for instructing the radiodevice to fall back from the first subscription. The fall-backindication is configured to be interpreted by the radio device as adirect instruction to change subscription from the first (current)subscription for activating the second subscription instead to enablecommunication between the radio device and the network side by means ofthe second subscription instead of the first subscription.

FIG. 5b is a schematic flow chart of another embodiment of a method ofthe connectivity service platform 2, of the present disclosure. Thesteps of falling back 52, receiving 53 a request message, and sending 54a reject message are as discussed in relation to FIG. 5a . Further, theplatform 2 may in some embodiments, prior to the falling back 52, store50 a fall-back policy 27, and possibly also send 51 a policy messagecomprising information about the stored 50 fall-back policy 27 to theradio device 5. Thereby, the radio device 5 may be informed of thefall-back policy 27 used by the platform 2, e.g. which subscription willbe used by the platform in case of fall back 52, allowing the radiodevice 5 to use this information for choosing to fall back to the samesubscription in case it receives a fall-back indication as part of areject message. The fall-back policy 27 may be predetermined andreceived by the platform 2 from outside of the platform, and then storedin the platform. The fall-back policy may be specific for the individualradio device 5 or eUICC 6.

FIG. 6a is a schematic flow chart of an embodiment of a method of theradio device 5, of the present disclosure. The radio device 5 sends 62 arequest message uplink via a wireless network connection of a firstsubscription of the radio device 5. This request message is typicallyreceived by a platform 2 as discussed herein. Then, the radio device 5receives 63 a reject message from the connectivity service platform 2,in response to the sent 62 request message. As also discussed inrelation to the method performed by the platform 2, the reject messagecomprises a fall-back indication instructing the radio device 5 to fallback from the first subscription. As a consequence of the receivedfall-back indicator, the radio device falls back 64 in accordance withthe received 63 fall-back indication, to a second subscription of theradio device, thereby enabling the radio device 5 to obtain a wirelessnetwork connection of the second subscription instead of the firstsubscription. Provided that the fall-back is successful and both theplatform 2 and the radio device 5 have activated the secondsubscription, the wireless network connection of the second subscriptioncan be set up.

FIG. 6b is a schematic flow chart of another embodiment of a method ofthe radio device 5, of the present disclosure. The steps of sending 62 arequest message, receiving 63 a reject message, and falling back 64 areas discussed in relation to FIG. 6 a.

Further, the method of the radio device may comprise, typically prior tothe sending 62 of the request message, receiving 60 a policy messagee.g. from the platform 2 or from another network node, comprisinginformation about a platform fall-back policy 27, i.e. the fall-backpolicy of the platform 2. The radio device may then store 61 a devicefall-back policy 37 based on said received 60 policy message. Typically,the device fall-back policy is the same as, or otherwise corresponds to,the platform fall-back policy 27, e.g. “in case of fall-back, changesubscription to (a specified) fall-back subscription”. If the respectivefall-back policies prompt both the device and the platform to fall backto the same subscription, the fall-back may be successful. When theradio device 5 has a stored device fall-back policy 37, the receivedfall-back indication may instruct the radio device 5 to activate thestored fall-back policy 37, whereby the falling back 64 may be inaccordance with the stored fall-back policy.

FIG. 7 is a schematic signalling diagram illustrating embodiments of thepresent disclosure. The platform 2, comprising the HLR 28, has fallenback from the first subscription to the fall-back (second) subscriptionwith a fall-back IMSI for the eUICC 6 identifier (ID) of the radiodevice 5 (here called User Equipment, UE). The UE 5 sends 62 the requestmessage 71 (here exemplified with a registration request) using the oldIMSI i.e. of the first subscription. The request message 71 a isreceived by the old MNO 7 and forwarded (message 71 b) to the HLR 28 ofthe platform 2. However, the old IMSI is no longer active in theplatform 2, but there is information stored therein, for that IMSI orother identifier of the radio device 5, instructing the platform to senda fall-back indication to the radio device 5. Thus, the platform 2 sends54 the reject message 72 (herein a registration reject message)comprising the fall-back indication. Again, the message (as message 72a) is received by the old MNO 7 and forwarded (message 72 b) to theradio device 5. Having received 63 the reject message 72, the radiodevice instructs (signal 73) its eUICC 6 to change IMSI from the currentfirst subscription to the fall-back second subscription, i.e. to fallback 64. The eUICC responds with a refresh command 74, where after theradio device 5 may send a new attach request 75 using the fallback IMSIof the second subscription.

In some embodiments of the present disclosure, the fall-back indicationis configured for instructing the radio device 5 to activate a fall-backpolicy 37 stored in the radio device. Thus, the second subscription neednot be specifically identified by the fall-back indication, since thefall-back policy 37 specifies which subscription to fall back to, i.e.the second subscription.

In some other embodiments, the fall-back indication identifies thesecond subscription and is configured for instructing the radio device 5to fall back to said second subscription. In this case, no stored devicefall-back policy may be needed.

In some embodiments of the present disclosure, the falling back 52comprises storing instructions for sending the reject message 72comprising the fall-back indication in response to receiving the requestmessage 71 from the radio device 5. The BSS 3 may thus instruct the HLRto store the instructions in order for the fall-back indication to besent to the radio device 5 if it tries to use the first subscription.Thus, in some embodiments, the instructions for sending the rejectmessage 72 are stored in an HLR 28 in the platform 2, e.g. by a businesssupport system (BSS) 3 in the platform 2. However, in some otherembodiments, the instructions for sending the reject message 72 arestored in a serving general packet radio service (GPRS) support node,SGSN, in the platform 2, e.g. by the HLR 28 or the BSS 3 via the HLR 28in the platform 2. It may be convenient to store the information in theSGSN because it is also possible for HLR to send this instructionsfurther to SGSN, so that SGSN can respond with the fall-back indicationvia the reject message directly to the devices, when SGSN receives therequest message 71 from the device 5. In that case there is no need totalk to HLR 28. To be more concrete, authenticationrequest/attach/location update request etc (examples of request messages71) are handled (rejected) by HLR 28, while mobile originated (MO) shortmessage service (SMS) request, packet data protocol (PDP) request, etc(other examples of request messages 71) can be handled (rejected) bySGSN directly, without need to involve the HLR 28. In some embodiments,the falling back 52 comprises removing the stored instructions afterhaving sent 54 the reject message 72. For instance, the fall-backindication may be removed from the platform 2, e.g. the HLR 28 and/orSGSN after the platform 2 has received a request message (e.g. a anattach request) from the radio device 5 using the second subscription,indicating that the device 5 has successfully changed to the secondsubscription and attaches to the network HLR/SGSN via said secondsubscription.

In some embodiments of the present disclosure, the request message 71 isa registration request for registering, or an attach request forattaching, or a location update request for updating the location of, oran authentication request for authenticating, or a short message service(SMS) request from, or a packet data protocol (PDP) context create oractivation request from, the radio device via the first subscription.

In some embodiments of the present disclosure, the reject message 72 isa signalling reject message or a traffic reject message, or any othersuitable reject message for embodiments of the request messages 71discussed herein, which has been modified to include a failure codecomprising the fall-back indication.

In some embodiments of the present disclosure, the platform 2 is enabledto communicate with the radio device 5 comprising an embedded UniversalIntegrated Circuit Card (eUICC) 6. However, also radio devices withother UICC or subscriber identity module (SIM) card or element may beused with embodiments of the present disclosure.

Example

Reference is made to FIG. 8. The premise for this proposed example isthat both the radio device 5 and the platform 2 have enabled, and arepossible communicating by means of, the first subscription of MNO 7.

Step A—Network side (BSS 3, HLR 28) detects a network connectivityfailure.

Step B—Network side executes its Fall-back policy 27. In the case ofnetwork connectivity failure, BSS Subscription Fall-back Component (SFC)25 determines to fall-back 52 to e.g. provisioning subscription (IMSI).Both BSS 3 and HLR 28 enable the provisioning (second) subscription, anddisable the current (first) subscription of MNO 7.

Step C—BSS Subscription Fallback Component (SFC) 25 sends a fall-backmessage to HLR, the fall-back message indicates that the specificeUICC(ID) has changed active subscription from MNO 7 IMSI toprovisioning subscription (MNO 8 IMSI), and that the device 5/eUICC 6shall re-attach to the network using the second subscription (IMSI),instead of the first subscription IMSI.

Step D—If no fall-back policy 37 has been implemented on the device5/eUICC 6, the device/eUICC still tries to attach to the network byusing the old MNO 7 IMSI. The request message 71 (incl. authenticationrequest, location update request, etc) of the MNO 7 IMSI is received 53by platform 2 HLR 28 registration signaling handler.

Step E—The HLR registration signaling handler recognizes that the MNO 7IMSI is in deactivated state or even not provisioned in the HLR 28.However, it also recognizes that there is fall-back information storedfor this IMSI and eUICC(ID), which indicates that the eUICC(ID) haschanged active subscription from MNO 7 IMSI to the MNO 8 provisioningIMSI. HLR registration signaling handler shall thus respond with theattach reject message comprising the fall-back indicator.

Step F—The device/eUICC registration signaling handler receives 63 theattach reject message including the fall-back indictor. It shall analyzethe fall-back indicator, and then notifies the eUICC Subscription changecomponent (SCC) 34 to enable and activate the MNO 8 provisioningsubscription (IMSI), and disable the MNO 7 IMSI in the eUICC 6.

Step G—eUICC 6 shall then enable and activate the MNO 8 provisioningsubscription, and disable and deactivate the current subscription of MNO7. eUICC 6 shall notify the radio device 5 to do a refresh command 74 inorder to trigger the reattach request to the network.

Step H—The device 5/eUICC 6 reattaches to the network by sending theregistration request 75 using the new (provisioning) IMSI, instead ofthe old MNO 7 IMSI. The new (provisioning subscription) IMSI is nowactive on both network side and eUICC side, therefore the eUICC 6 canrecover the connectivity successfully with the provisioning IMSI, andthe fall-back is successful.

Below follow some other aspects of the present disclosure.

According to an aspect of the present disclosure, there is provided aconnectivity service platform 2 for a communication network 1. Theplatform comprises means (e.g. the processor circuitry 21 in cooperationwith the communication interface 29) for being enabled to communicatewith a radio device 5 via a wireless network connection of a firstsubscription of the radio device. The platform 2 also comprises means(e.g. the processor circuitry 21, such as the fall-back detector 22(possibly of the SFC 25) and/or the SCC 24) for falling back 52 to asecond subscription, thereby enabling the connectivity service platform2 to communicate with the radio device 5 via a wireless networkconnection of said second subscription of the radio device instead ofthe first subscription. The platform 2 also comprises means (e.g. theprocessor circuitry 21 in cooperation with the communication interface29) for receiving 53 a request message 71 from the radio device 5 viathe network connection of the first subscription. The platform 2 alsocomprises means (e.g. the processor circuitry 21 in cooperation with thecommunication interface 29) for sending 54 a reject message 72 to theradio device 5, in response to the received 53 request message 71 and inview of the platform 2 having fallen back 52 to the second subscription.The reject message 72 comprises a fall-back indication (e.g. from thestorage 26, such as the HLR 28) for instructing the radio device to fallback from the first subscription.

According to another aspect of the present disclosure, there is provideda radio device 5 for a communication network 1. The radio devicecomprises means (e.g. the processor circuitry 31 in cooperation with theradio communication interface 39) for sending 62 a request message 71uplink via a wireless network connection of a first subscription of theradio device 5. The radio device also comprises means (e.g. theprocessor circuitry 31 in cooperation with the radio communicationinterface 39) for receiving 63 a reject message 72 from a connectivityservice platform 2, in response to the sent 62 request message 71. Thereject message comprises a fall-back indication instructing the radiodevice 5 to fall back from the first subscription. The radio device alsocomprises means (e.g. the processor circuitry 31, such as the fall-backdetector 32 (possibly of the SFC 35) and/or the SCC 34) for falling back64 in accordance with the received 63 fall-back indication, to a secondsubscription of the radio device, thereby enabling the radio device 5 toobtain a wireless network connection of the second subscription insteadof the first subscription.

The present disclosure has mainly been described above with reference toa few embodiments. However, as is readily appreciated by a personskilled in the art, other embodiments than the ones disclosed above areequally possible within the scope of the present disclosure, as definedby the appended claims.

1. A method performed by a connectivity service platform in acommunication network, the platform being enabled to communicate with aradio device via a wireless network connection of a first subscriptionof the radio device, the method comprising steps of: falling back, bythe connectivity service platform, to a second subscription, therebyenabling the connectivity service platform to communicate with the radiodevice via a wireless network connection of said second subscription ofthe radio device instead of the first subscription; receiving, by theconnectivity service platform, a request message from the radio devicevia the network connection of the first subscription, wherein the firstsubscription is no longer valid in the connectivity service platform;and sending, by the connectivity service platform, a reject message tothe radio device, in response to the received request message and inview of the platform having fallen back to the second subscription, thereject message comprising a fall-back indication for instructing theradio device to fall back from the first subscription; and, wherein theconnectivity service platform performs in sequence the falling backstep, then the receiving step, and then the sending step.
 2. The methodof claim 1, wherein the fall-back indication is configured forinstructing the radio device to activate a fall-back policy stored inthe radio device.
 3. The method of claim 1, wherein the fall-backindication identifies the second subscription and is configured forinstructing the radio device to fall back to said second subscription.4. The method of claim 1, wherein the falling back comprises storinginstructions for sending the reject message comprising the fall-backindication in response to receiving the request message from the radiodevice.
 5. The method of claim 4, wherein the instructions for sendingthe reject message are stored in a home location register (HLR) or aserving general packet radio service (GPRS) support node (SGSN) in theconnectivity service platform.
 6. The method of claim 4, wherein thefalling back comprises removing the stored instructions after havingsent the reject message.
 7. The method of claim 1, wherein the requestmessage is one of a registration request for registering; or an attachrequest for attaching; or a location update request for updating thelocation of; or an authentication request for authenticating; or a shortmessage service (SMS) request from; or a packet data protocol (PDP)context create or activation request from; the radio device via thefirst subscription.
 8. The method of claim 1, wherein the connectivityservice platform is enabled to communicate with the radio devicecomprising an embedded Universal Integrated Circuit Card (eUICC).
 9. Themethod of claim 1, wherein the connectivity service platform beforeperforming the falling back step performs the following steps: storing,by the connectivity service platform, a fall-back policy; and sending,by the connectivity service platform, a policy message comprisinginformation about the fall-back policy to the radio device.
 10. Aconnectivity service platform for a communication network, theconnectivity service platform comprising: processor circuitry; andstorage for storing instructions executable by said processor circuitrywhereby said connectivity service platform is operative to: communicatewith a radio device via a wireless network connection of a firstsubscription of the radio device; fall back to a second subscription,thereby enabling the connectivity service platform to communicate withthe radio device via a wireless network connection of said secondsubscription of the radio device instead of the first subscription;receive a request message from the radio device via the networkconnection of the first subscription, wherein the first subscription isno longer valid in the connectivity service platform; send a rejectmessage to the radio device, in response to the received request messageand in view of the platform having fallen back to the secondsubscription, the reject message comprising a fall-back indication forinstructing the radio device to fall back from the first subscription;and, wherein the connectivity service platform is operable to perform insequence the communicate operation, then the fall back operation, thenthe receive operation, and then the send operation.
 11. The connectivityservice platform of claim 10, wherein the fall-back indication isconfigured for instructing the radio device to activate a fall-backpolicy stored in the radio device.
 12. The connectivity service platformof claim 10, wherein the fall-back indication identifies the secondsubscription and is configured for instructing the radio device to fallback to said second subscription.
 13. A method performed by a card in aradio device, wherein the radio device is performing a fall back step ina communication network from a first subscription to a secondsubscription, the method comprising steps of: receiving, from the radiodevice, instructions to change an old International Mobile SubscriberIdentity (IMSI) from the first subscription to a new IMSI for the secondsubscription; and, sending, to the radio device, a refresh command. 14.The method of claim 13, wherein the card is: an embedded UniversalIntegrated Circuit Card (eUICC); a removable Universal IntegratedCircuit Card (UICC); or a Subscriber Identity Module (SIM) card.
 15. Themethod of claim 13, wherein the first subscription and the secondsubscription are with a same Mobile Network Operator (MNO).
 16. Themethod of claim 13, wherein the first subscription is with a firstMobile Network Operator (MNO) and the second subscription is with asecond Mobile Network Operator (MNO).
 17. A card in a radio device,wherein the radio device is performing a fall back operation in acommunication network from a first subscription to a secondsubscription, the card is configured to: receive, from the radio device,instructions to change an old International Mobile Subscriber Identity(IMSI) from the first subscription to a new IMSI for the secondsubscription; and, send, to the radio device, a refresh command.
 18. Thecard of claim 17, wherein the card is: an embedded Universal IntegratedCircuit Card (eUICC); a removable Universal Integrated Circuit Card(UICC); or a Subscriber Identity Module (SIM) card.
 19. The card ofclaim 17, wherein the first subscription and the second subscription arewith a same Mobile Network Operator (MNO).
 20. The card of claim 17,wherein the first subscription is with a first Mobile Network Operator(MNO) and the second subscription is with a second Mobile NetworkOperator (MNO).